Add to Database

To access this dialog:

Using the Home ribbon, select Database | Add to Database. Select the Open Pit tab.

The Survey Export dialog is used to commit loaded open pit data objects to the survey database, generating files within the current database structure.

The Add to Database panel is used to commit data to the expected database location in an open pit survey database, based on the type of data you are adding. You can add data that is specific to a pit, area or ROM, or at a more general level (all pits, all areas, all ROMs).

You can view files that have been added to the active database using the Project Data control bar or the Browse Database tool.

Underground survey data is added using the Underground tab.

First, review the Pit, Area and ROM assignment for the current operation. You will be adding data to the context listed here (or you can choose a more general data Scope - see below), but you can edit any item by clicking the corresponding browse button. This displays the Database Settings screen, allowing you to choose another predefined pit, area or ROM.
Select the name of a Surveyor (as defined in your Survey Database settings), then select the Survey date using the date picker provided. Both Surveyor and Survey Date will be embedded within the data that is committed to the current survey database.
Select the Type of Data you are committing to your database. This will provide a list of all loaded objects of that type in the Data Source list.

Alternatively, you can browse your project (or disk) for a file that you wish to commit to the database, using the ellipsis button (...).
Next, select a Data Source. There are three ways to do this;

Select the name of a loaded object from the dropdown list provided.
Use the Data Source browse button to locate a file on disk that you wish to add to the database with the current context. For wireframe files, select the triangle file of the point/triangle pair.
Use the pick button to interactively select data in the 3D window. You will only be able to pick data of the type selected in the Type of Data dropdown list.

Select the Scope of the data you are adding (see Data Scope within the Survey Database Hierarchy)
If you don't wish to use the default data name (e.g. "DesignSurface_MyPit_MyArea...", "NaturalSurface_MyPit_MyArea..." and so on, you can enter your own file description into the Reference Name field. This will be used to prefix the generated file name, e.g. "MyName_MyPit_MyArea".

The only exception to this is the Pit Blast Bottom Surface data type, where a Reference Name must be provided. For all other data types, the custom name is optional.
When you are ready, click Add to Database to generate the relevant files and update your project database to point to them. Existing files can be overwritten if you are permitted to do so. The selected data will now be available to the survey reporting utilities.

Surface data will be linked to the Survey Date, allowing for time period selection in subsequent reporting panels.

Data can only be selected in any of the Survey Report panels if it has been added to the Studio Survey Database.

The following data type options are available:

Designed Pit Strings: strings representing design surface shapes that have been planned and are expected. This data is not used explicitly in cut and fill volume calculations but can be useful reference data for QA/QC purposes. Can be added as [Global], [Current Pit] or [Current Area] Scope.
Designed Pit Surfaces: open wireframe surfaces that have been planned and are expected. These are compared with the ground data for the same time period, using the Compliance to Design report facility. Can be added as [Global], [Current Pit] or [Current Area] Scope.
End of Period Pit Strings: strings representing end of period surface shapes that have been designed and are expected. This data is not used explicitly in cut and fill volume calculations but can be useful reference data for QA/QC purposes. Can be added as [Global], [Current Pit] or [Current Area] Scope.
End of Period Pit Surfaces: open wireframe surfaces that have been generated, say, using Studio OP's End-of-period Surface tool. These are compared with the current ground data for the same period, using the Compliance to Plan report. Can be added as [Global], [Current Pit] or [Current Area] Scope.
Natural Pit Strings: strings representing natural pit surfaces (for example, elevation contours) that are a result of ground survey. This data is not used explicitly in cut and fill volume calculations but can be useful reference data for QA/QC purposes. Can be added as [Global], [Current Pit] or [Current Area] Scope.
Natural Pit Surfaces: a natural surface (unmined topography) is used in the end-of-month pit (Pit Actual) report to determine the overall volume mined as well as the per-period volume. Can be added as [Global], [Current Pit] or [Current Area] Scope.

If specified, the Pit Actual report will generate a natural-previous and natural-current volume report, in addition to a previous-current excavation assessment.

A natural pit surface doesn't have to be specified for Pit Actual reporting. If no surface is specified, cut and fill data will be provided for the previous and current surface only.
Pit Blast Bottom Strings: strings representing designed pit blast bottom shapes. This data is not used explicitly in blast volume calculations but can be useful reference data for QA/QC purposes. Can be added as [Global], [Current Pit] or [Current Area] Scope.
Pit Blast Bottom Surfaces: choose this option if you need to add contact/strata surface/volume data to the database. This will be used during blast volume calculation as a limiting surface for the projected blast volume. More about calculate-blast-volume... Can be added as [Global], [Current Pit] or [Current Area] Scope.
Pit Excavation Boundaries: pit boundaries are closed strings that can be used to constrain volume reporting within a given perimeter. This data can be used in the Pit Actual, Compliance to Design and Compliance to Plan reports. Can be added as [Global], [Current Pit] or [Current Area] Scope.
ROM Base Strings: strings representing ROM surface shapes, as surveyed. This data is not used explicitly in ROM calculations but can be useful reference data for QA/QC purposes. Can be added as [Global], [Current Pit] or [Current Area] Scope.
ROM Base Surfaces: a ROM surface upon which stockpile surfaces will grow. This is used to calculate the Base Stockpile Surface in the end of month ROM report. Can be added as [Global] or [Current ROM] Scope.
ROM Stockpile Strings: strings representing ROM stockpile shapes, as surveyed. This data is not used explicitly in ROM calculations but can be useful reference data for QA/QC purposes. Can be added as [Global], [Current Pit] or [Current Area] Scope.
ROM Stockpile Boundaries: string objects representing the limiting perimeter for stockpile survey reports (ROM report). Can be added as [Global] or [Current ROM] Scope.

Before you can generate a stockpile volume report, you must have at least one string object in the survey database that represents the base string for each stockpile you wish to report. For multiple stockpiles, this string data must contain the following attributes:

ROMNAME: the name of the current run-of-mine surface upon which the stockpiles are positioned.
STKNAME: the name of the stockpile. For each unique STKNAME value, a separate volume will be reported.

For example, the string file may contain two closed strings; the first is represented by the ROMNAME of "ROM1" and a STKNAME of "Stockpile_1". The second is also determined by a ROMNAME of "ROM1" (they both share the same base surface) and a STKNAME of "Stockpile_2". The resulting report will contain volume calculations for both stockpiles independently based on the difference between the specified Base Stockpile Surface and Top Stockpile Surface. More about the ROM report...

ROM stockpile boundaries can be created within Studio Survey using the Home ribbon's Boundaries | ROM Stockpile option, which displays the ROM Stockpile Boundary panel. You can also use this screen to add the boundary string to the database, mimicking the above function. Generally, it is quicker and easier to create and add boundary strings to the database using the ROM StockpileBoundary panel.

ROM Stockpile Surfaces: surveyed stockpile data representing the stockpile surface for a given time period. Current and previous stockpile surfaces are used to generate ROM reports. Can be added as [Global] or [Current ROM] Scope.
Surveyed Pit Strings: string data resulting from ground survey. Whilst not used directly in ROM calculations, such data can be useful reference data for QA/QC purposes.
Surveyed Pit Surfaces: a pit surface represents the survey data for a pit for a given time period and represents the ground data to be compared with either a previous pit surface (Pit Actual report), a design surface (Compliance to Design report) or an end-of-period planned surface (Compliance to Plan report). Can be added as [Global], [Current Pit] or [Current Area] Scope.

If you add wireframe data to the database, and the wireframe(s) in question have a corresponding georeferenced texture file (.bmpx, .pngx or similar), the texture file will automatically be copied to the database in the same location.

Data Scope

The Add to Database screen is used to configure data scope, when it is added to the database.

By default, when you add to the Survey Database, data represents the state of the mine at a given date, and applies to a particular data context, such as a pit and area for open pit surveys (or decline, area, level and stope for underground operations). You can also create data at a more general level.

For example, you may have a string file containing all excavation boundaries for all areas of a pit. In this scenario, you could add the boundary string file to the [Current Pit] level, meaning it will be selectable in all EOM pit reports for the current pit, regardless of the area designation. Similarly, if your project encompassed multiple pits, and the string data contained all boundaries for all pits, it could be added at the [Global] level.

An underground example could be a set of planned design strings representing developments related to the same decline, and applying to multiple areas. In this case, the [Development Design Strings] would be added to the [Current Area]

If you are adding open pit data for a Pit Actual, Design Compliance or Plan Compliance report, you can add data at one of three levels:

Current Area: data added at this level relates to a specific area and pit and will always be used in a report if it exists, otherwise, data for the same Survey date at the Pit or Global level will be used.
Current Pit: data added at this level is accessible to any EOM pit report, regardless of the Area for which the report is being generated, providing area-specific data (see above) for the same Survey date does not exist.
Global: data added at this level is accessible to any EOM pit report, regardless of pit or area reporting context, providing data does not exist at a lower level.

If you are adding data for an open pit ROM report, you can add data at one of two levels:

Current ROM: the ROM data will be specific to a ROM. When a ROM report is run for the given Survey date, this data will be used in preference to any global data that may exist (for the same Survey date).
Global: data added at this level will be (potentially) available to any ROM report for the same Survey date, providing more specific data isn't available (i.e. hasn't been added at the Current ROM level - see above).